taxcredit-engine__describe_agent

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

No annotations are provided, so the description carries full burden. It does not disclose side effects, auth requirements, or rate limits. While 'return' implies read-only, the description lacks explicit behavioral disclosure, making it less transparent.

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 a single concise sentence with a domain bracket prefix. It is front-loaded and contains no unnecessary words. Could be slightly more structured, but highly efficient.

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 zero-parameter, no-output-schema tool, the description is sufficiently complete. It specifies the agent domain and return content (capabilities, version, pricing). Minor gap: no mention of output format, but acceptable for simplicity.

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?

No parameters exist, and schema coverage is 100%. Per guidelines, baseline is 3 even with no param info in description. The description adds domain context but no parameter-specific meaning.

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 returns 'fleet-standard capabilities, version, and pricing' for the taxcredit-engine agent, with the domain prefix clarifying it is for clean-energy tax-credit scenarios. This distinguishes it from other describe_agent tools and gives specific content.

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 explicit when-to-use or when-not-to-use guidance is given. For a simple retrieval tool with no parameters, usage is self-evident, but the description does not provide alternatives or exclusions, meeting only the minimum adequacy.

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