alt_capability_manifest

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

No annotations provided; description uses 'Return' implying read-only, but does not explicitly state nondestructive nature or potential side effects. Adequate but not explicit.

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?

Single sentence that efficiently conveys purpose and content. Front-loaded with main action. Could benefit from slight restructuring for clarity, but no wasted words.

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?

No output schema, so description should hint at return format. Mentions 'machine-readable' but not specific (JSON, etc.). Parameters explained in schema, but overall lacks detail on what the manifest looks like. Adequate for a simple retrieval tool.

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?

Input schema covers both parameters with descriptions (100% coverage). Description adds no extra parameter-level details beyond what schema provides. Baseline score of 3 applies.

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?

Description clearly states it returns 'Alt manifest' with specific contents (setup, SDK boundary, PAIDEIA rules, action-to-tool recipes). Distinguishes from siblings like list_paideia_actions by being comprehensive, but could be clearer on how it differs.

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?

No guidance on when to use this tool vs alternatives like list_paideia_actions or alt_workflow_guide. Missing criteria for selection among similar sibling tools.

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