Show Submittal

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds API endpoint and version details but does not disclose behavioral traits like pagination behavior (page/per_page parameters are present but unexplained) or response structure beyond 'JSON object'.

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 reasonably concise with three sentences and a link, front-loading the purpose. Some redundancy with schema (required parameters) is acceptable, but overall efficient.

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?

The description does not explain why pagination parameters (page, per_page) are included for a single-resource endpoint, nor does it detail the return JSON structure (no output schema). This leaves ambiguity for the agent.

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?

Schema coverage is 100%, so parameters are well-documented. The description explicitly highlights required parameters (project_id, id) and mentions URL path structure, but adds no additional meaning beyond the schema.

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 the tool returns detailed information on a specified Submittal and specifies required parameters. However, it does not differentiate from sibling tools like list_submittals or show_submittal_in_pdf_format.

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?

It says to use this tool to fetch full details by identifier, which implies usage context, but does not provide when-not-to-use guidance nor explicitly name alternatives.

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