Get Manifest by Manifest State ID

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

With no annotations provided, the description carries the transparency burden. It clarifies that a single full manifest is returned, which is useful, but it does not disclose error handling, permissions, or any filtering behavior. The disclosure is partial and leaves some behavioral aspects unaddressed.

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 extremely concise: two sentences that directly state the action and result. It is front-loaded with the verb and leaves out any redundant information, earning full credit for efficiency.

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 simplicity of the tool (one parameter, no output schema, no annotations), the description adequately communicates the purpose and return value ('single manifest', 'full manifest'). It could have added details about error cases or output format, but the current level is sufficient for the tool's straightforward nature.

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 provides 100% coverage for the single parameter, including a description ('The manifest state ID to retrieve'). The tool description does not add any additional semantics beyond what the schema already states, so the baseline score of 3 is appropriate.

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 'Retrieve a single manifest by its manifest state ID' with a specific verb and resource. It distinguishes from siblings like get_files_by_manifest_state_id by explicitly indicating a manifest (not files) and a single result, making the tool's purpose unambiguous.

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 the tool should be used when a manifest state ID is available and the full manifest is needed, but it does not explicitly provide exclusions or alternatives like get_manifests_by_schema_name. This is adequate but lacks explicit comparison to sibling tools.

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