pbip_export_summary

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

No annotations and description does not disclose any behavioral traits (e.g., read-only, permissions, side effects). Agents have no insight into tool behavior beyond basic action.

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 is concise and front-loaded, but lacks necessary details for a tool with one undocumented parameter. Considered minimal viable.

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 must explain output format but does not. Parameter clarification missing. Sibling tools list is large but no context on usage. Very incomplete.

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 has 0% description coverage for parameter 'projectPath'. Description does not explain what 'projectPath' should be (file path, project ID?); no additional meaning provided.

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 verb 'Export' and resource 'structured JSON summary of a PBIP project'. It is specific and distinguishes from sibling tools like pbip_describe_project or pbip_create_project.

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 versus alternatives like pbip_describe_project. No conditions, prerequisites, or exclusions provided.

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