getOrgInfo

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

No annotations provided; description must disclose behavior. It does not mention read-only nature, caching, or any side effects. The tool may be read-only but fails to confirm.

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?

Extremely concise (one sentence), but undermines clarity. Front-loads verb and resource but omits necessary details, making it under-specified rather than efficiently concise.

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 no output schema and many sibling get tools, the description fails to provide sufficient context. A user cannot know what fields or entities are returned.

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, so baseline is 4, but the description adds no meaning beyond the tool name. It does not clarify what 'info' entails or how the result is structured.

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 'Get organization info' is a generic verb-resource but lacks specificity. It does not differentiate from sibling tools like getMe, getMemberByAccount, etc. Needs to define scope or content of 'org info'.

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 such as getMe or getCompany (implied). Missing context about prerequisites or when retrieval is appropriate.

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