get-routine

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'returns all details' but does not state that it is read-only, mention auth requirements, or describe potential errors. The name implies idempotency, but the description adds no behavioral context beyond the obvious.

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 two sentences and gets to the point quickly. The phrase 'using the direct endpoint' is slightly redundant but does not harm clarity. It is efficient overall.

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?

Given the tool's simplicity (one parameter, no output schema), the description is minimally complete. It explains the input and says returns details, but leaves the output structure undefined. For an AI agent, more specificity about the returned details would improve action planning.

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 input schema has one parameter (routineId) with no description, and the schema description coverage is 0%. The description adds minimal value by saying 'by its ID,' which is already implied by the tool name. It does not explain the format or source of the ID.

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 gets a routine by its ID, specifying the resource and action. It distinguishes from sibling tools like get-routines (plural) and get-routine-folder by focusing on a single routine.

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 use when you have a specific routine ID, but it does not explicitly mention when not to use it or contrast with sibling tools like get-routines for listing. No alternatives are suggested.

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