move_get_take

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

Annotations already declare readOnlyHint=true, and the description does not contradict that. It adds little behavioral detail beyond the purpose, such as response shape, error cases, or expand behavior, though an output schema is present and the operation is simple.

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 a single front-loaded sentence with no filler. Every word contributes to identifying the operation and target resource.

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 simple read tool with an output schema, read-only annotations, and a self-explanatory required take_id parameter, the description is mostly sufficient. It does not explicitly route the agent away from list/update siblings, but the operation is simple enough that an agent can call it correctly with the provided schema and annotations.

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 description coverage is 50%: the expand parameter is well documented, while take_id has no schema description. The phrase 'by id' lightly reinforces take_id's role, but the description does not add new meaning to either parameter beyond what the schema provides.

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 'Fetch a take by id' uses a specific verb and resource, clearly identifying a single-take read operation. The 'by id' qualifier distinguishes it from sibling list/update tools without requiring schema inspection.

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 this tool is for retrieving one take when its id is known, but it does not explicitly contrast it with alternatives like move_list_takes for browsing or move_update_take for modifications. Usage context is present but exclusion conditions are not stated.

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