get_organization_details

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

No annotations are supplied, so the description carries the burden, and it does disclose 'Read-only' — a meaningful safety signal. Beyond that it says nothing about authentication requirements, caching/staleness of fiscal settings, or whether it errors when no organization is connected, which is thin for a tool with zero annotation coverage.

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?

One sentence, front-loaded with the verb and resource, then the returned fields, then the read-only qualifier. No filler and nothing buried.

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?

With no output schema, the description usefully enumerates what the profile contains, which is exactly what the agent needs from a zero-parameter getter. It is nearly complete, missing only confirmation of behavior on a disconnected/unauthenticated state.

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 tool takes no parameters, so per the rubric the baseline is 4. The description correctly implies a single implicit scope (the connected organization) rather than accepting any identifier, which reinforces why no input is needed.

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 names a specific verb ('Get') and resource ('the connected organization's profile') and enumerates the fields returned — legal name, currency, fiscal settings, enabled modules. It does not, however, differentiate itself from the sibling get_enabled_modules, which overlaps with the last field it advertises.

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 contains no when-to-use guidance at all. It never says when this profile fetch is preferable to get_connection_status or get_enabled_modules, nor whether it should precede other org-scoped operations, leaving the agent to infer routing from names alone.

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