Show Resource Assignment

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

The description adds the API endpoint and version, complementing the readOnlyHint annotation. It mentions returning a JSON object but does not describe pagination behavior or potential side effects. No contradiction with annotations.

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 concise with four sentences, each serving a purpose: main action, usage, return type, and required parameters. It is front-loaded and 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 lacks explanation of pagination parameters (page, per_page) that appear in the schema, which implies possible list behavior, conflicting with the singular resource claim. Without an output schema, more detail on the returned JSON object would be beneficial.

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 description only repeats the required parameters (project_id, id) already in the schema. With 100% schema description coverage, this adds minimal value. The purpose of page and per_page parameters is not explained in the description.

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 shows details of a specific Resource Assignment and mentions it is for Schedule (Legacy) records. The verb 'Show' and resource are specific, but it could better distinguish from other resource-related show tools in the sibling list.

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 says 'Use this to fetch the full details of a specific Schedule (Legacy) records by its identifier,' providing clear usage context. However, it does not explicitly state when not to use it or mention alternative tools for similar resources.

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