get_platform_target

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

With no annotations provided, the description carries the full burden. 'Get details' implies a read-only operation, but the description does not disclose what 'details' includes, error behavior, or any side effects. It adds minimal context beyond the action itself.

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?

A single, efficient sentence with the verb front-loaded and no wasted words. It is concise and clearly structured.

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 getter with one required parameter, the description is minimally adequate, but with no annotations and no output schema, it lacks detail on the return structure, error cases, and any special behavior. It is sufficient for basic invocation but leaves gaps for edge cases.

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 covers the single 'id' parameter with a description ('Platform target ID'), achieving 100% coverage. The description adds no additional meaning about the parameter format, source, or constraints beyond what the schema already 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 clearly states the verb 'Get' and the resource 'platform target', and 'specific' indicates retrieval of a single entity by ID. This distinguishes it from list_platform_targets and other get_* target tools.

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 known platform target ID, but it does not explicitly mention when to use this tool vs list_platform_targets or provide any exclusions. No explicit guidance on preconditions or alternatives is given.

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