get_org

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

Discloses that it is a read operation (GET), specifies the HTTP endpoint, and describes the return fields and authentication behavior. No annotations are provided, so the description carries the full burden and does so thoroughly.

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?

Two sentences plus a fragment that directly convey purpose, usage, and parameters. 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?

For a simple read tool with one parameter and no output schema, the description covers all essential aspects: what it does, what it returns, who can use it, and how the parameter behaves.

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 schema already provides a description for org_id, and the tool description merely reiterates 'Params: org_id' without adding additional meaning or examples beyond the schema. Given 100% schema coverage, baseline 3 is appropriate.

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 reads one organization and lists the specific fields returned (org_id, display_name, tier, role). It distinguishes itself from sibling tools like list_orgs and other CRUD operations.

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?

Explicitly states who may use it ('Any active member') and describes the behavior for non-members (403 error). This provides clear when-to-use and context about authorization.

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