Get partner summary

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

The description offers minimal behavioral insight beyond the basic action. No annotations exist, so the description bears full burden; it omits safety, authentication, error handling, and return format details.

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?

While the description is a single sentence, it is underspecified rather than concise. It lacks necessary detail and does not earn its place by providing actionable information.

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 tool has 3 parameters, no output schema, and no annotations, the description is severely inadequate. It fails to explain what the tool returns, how to filter via parameters, or any 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?

Schema description coverage is 0%, and the description does not mention any parameters or their roles. The parameters 'id', 'company', and 'profile' have no explanations, leaving an agent without guidance on how to use them.

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 states 'Fetch one partner with a small business summary', which gives a general verb and resource. However, 'small business summary' is vague and does not differentiate from sibling tools like 'get_partner_detail' or 'get_partner_balance_summary'.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives such as 'get_partner_detail' for full details or 'get_partner_balance_summary' for financial data.

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