solidtime_organization_get

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the implicit-resolution behavior (env var fallback), but says nothing about failure modes such as a nonexistent organization or ambiguous multi-membership resolution, nor what the response contains.

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 short sentences with the core action front-loaded, so an agent can parse it instantly. The second sentence largely restates what the schema already says about the optional parameter, making it slightly redundant rather than wasteful.

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 single-resource read tool with one optional parameter, most of what's needed is present. With no output schema, however, the description never indicates what an organization record returns, leaving the agent to guess the payload shape.

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% and the schema entry already spells out the full fallback chain, including the memberships endpoint. The description repeats that fallback rather than adding new meaning (format, constraints, or effect on the lookup). Baseline 3 applies.

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?

States a specific verb and resource ("Get an organization") and pins it to an endpoint, so the agent knows exactly what object is fetched. It is clearly distinct from organization_create/update/delete siblings by implication, though it never names them or a list counterpart explicitly.

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 supplies a genuine precondition — organization_id may be omitted when SOLIDTIME_ORGANIZATION_ID is set — which tells the agent when the parameterless call is valid. It gives no guidance on when to call this versus other organization-related or membership/user tools, leaving selection to inference from the name.

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