get_organization

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

No annotations are provided, so the description carries the full burden. It clearly discloses that the operation is a 'Get' (implying read-only) and specifies the returned data fields. However, it does not explicitly state that the operation is safe or describe any potential side effects, though none are expected for a simple read.

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 concise sentence that front-loads the action and resource, followed by the key return fields. There is no wasted language, and every word contributes meaning.

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 and no annotations, the description satisfactorily explains what is returned (profile fields and follower count). It is complete enough for a simple tool with one optional parameter, though it could mention that there might be additional profile fields beyond those listed.

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% for the single parameter organization_id, which already explains the default behavior and expected format. The description adds no additional parameter meaning, so a baseline of 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's purpose with a specific verb ('Get') and resource ('Company Page's profile') while also specifying exactly what is returned (name, vanity, description, total follower count). This efficiently distinguishes it from sibling tools like get_follower_statistics, which likely provides more detailed stats rather than a profile summary.

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 implies usage for fetching an organization's profile and follower count but does not provide explicit guidance on when to use this tool versus siblings such as list_organizations or get_follower_statistics. No exclusions or alternatives are mentioned, so the context is only implied.

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