Get Account Info

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

Annotations already declare readOnlyHint=true and idempotentHint=true, which the description does not repeat. However, it adds useful behavioral context by mentioning the $expand parameter to include custom fields and plan info, enhancing transparency beyond annotations.

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 with two sentences: first stating the purpose and listing example fields, second giving a usage tip. No extraneous 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?

The tool is simple (read-only, no required parameters, no output schema). The description covers what data is returned and how to customize via expand/select. Given the sibling tools and annotations, it is fully complete for an agent to invoke correctly.

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 100% (both 'expand' and 'select' are well-described). The description adds value by providing concrete examples of how to use $expand and $select, giving practical guidance for parameter usage.

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 it retrieves information about the current Ploomes CRM account, listing specific fields like company Name, Email, Phone, etc. It differentiates well from siblings which focus on other entities (contacts, deals, etc.) as this is the only account-level tool.

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 explicitly states it provides account info, giving clear context for when to use it. It does not explicitly mention when not to use it, but the purpose is sufficiently specific given the sibling tools focus on different resources.

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