Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context about returning a full schema.org page and accepting multiple identifier forms, but does not disclose any additional behavioral details like not-found handling or response size.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one efficient sentence, front-loaded with the core purpose ('Full schema.org page for one entity') and immediately followed by the accepted identifier forms. There is no filler or repetition of structural schema information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only tool with no output schema, this description is largely complete: it explains what the tool returns and how to identify the entity. The remaining gap is the lack of explicit routing among the many get_* sibling tools, but that is a minor omission given the simple contract.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides only a bare entity_id string with 0% description coverage. The description fully compensates by defining the canonical id syntax (seaweb://{vertical}/{slug}), confirming legacy ids are accepted, and clarifying that a unique bare slug also works. This is strong parameter guidance for a single-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: it returns the full schema.org page for one entity. It also specifies the accepted identifier forms. It does not explicitly name or differentiate from overlapping siblings like get_details, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool: when you have a canonical id, legacy id, or unique bare slug and want the full schema.org page. However, it gives no explicit guidance about when not to use it or which sibling tool should be preferred for more specific entity lookups.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.