get_team_deployment_context

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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the description doesn't need to restate safety. The description adds one behavioral fact: it returns the concrete home region used for default deployments, not a range or configuration. No contradiction with annotations. It does not disclose details like whether fallback logic or caching is involved, but the simple scope is adequately transparent.

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, no filler, directly front-loads the point: 'Return the concrete home region used for default deployments by a team.' Every word earns its place.

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-only single-parameter tool with full schema coverage and an output schema, the description is nearly complete. It could optionally mention what to do if a team has no default region, but that gap is minor given the output schema exists.

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 only parameter team_id has a schema description 'The ID of the team.' Schema description coverage is 100%, so the schema already explains the parameter. The description does not add format, source, or example guidance for team_id. 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?

States a specific action (return) and resource (concrete home region used for default deployments by a team). The scope is clear, but it doesn't distinguish itself from sibling tools beyond the 'get_team_deployment_context' name; however, the phrase 'concrete home region' and 'default deployments' gives enough specificity.

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 context says this retrieves deployment context for a team, which implies it is for inspecting where a team deploys by default, but it does not explicitly state when to prefer it over sibling tools like get_workspace or list_workspaces. No alternatives or exclusions are mentioned.

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