get_org

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

No annotations are present. The description indicates a read operation ('Get details'), which is clear, but it fails to disclose any behavioral traits such as what exactly 'details' includes, authentication needs, or potential side effects. It is adequate for a simple read tool but not transparent beyond the surface.

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 sentence with no unnecessary words, ensuring the purpose is front-loaded and immediately clear.

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 absence of an output schema, the description should explain what 'details' are returned. It does not, leaving the agent without knowledge of the tool's output. The description is underspecified for a tool with no structured return information.

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?

The parameter 'org' is fully described in the schema (100% coverage). The tool description does not add any additional meaning beyond what the schema already provides. A score of 3 reflects the baseline given high schema coverage.

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 details of an organization' uses a specific verb 'Get' and resource 'organization', clearly distinguishing it from sibling tools like 'create_org', 'edit_org', and 'delete_org'. No ambiguity.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when not to use it.

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